-
-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perf(parser): lex JSXText with memchr #2558
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @overlookmotel and the rest of your teammates on Graphite |
CodSpeed Performance ReportMerging #2558 will improve performances by 8.03%Comparing Summary
Benchmarks breakdown
|
0852391
to
5857db3
Compare
1082bd3
to
ca4e27a
Compare
51e0e5c
to
47e1a42
Compare
@overlookmotel can you restack this, this PR is going off the rails 😅 |
ca4e27a
to
e109e78
Compare
"We prefer smaller PRs". Well you asked for it! Restacked now. FYI The various other draft PRs branching off this are things I'd hoped would be simple to merge as a single stack, but they're not having the positive effects I'd hoped for on benchmarks, so want to fiddle with them a bit more. |
Lexing JSXText only requires searching for 2 possible characters (`<` and `{`), so can use `memchr`.
This reverts commit 04a69de.
This reverts commit 04a69de.
Lexing JSXText only requires searching for 2 possible characters (`<` and `{`), so can use `memchr`.
Lexing JSXText only requires searching for 2 possible characters (
<
and{
), so can usememchr
.